Add a "Debugger Memory Map" sidebar panel that lists the target's mapped
regions (Start / End / Size / Permissions / Name), mirroring the existing
Debugger Modules panel. It refreshes on the target-stopped event via
DebuggerController::GetMemoryMap(), supports filtering, copy/copy-all, and
double-click / context-menu navigation to a region's start or end.

This gives a UI to exercise and validate the memory-map data added in the
previous commit before the per-region-segment follow-up.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Enumerate the target's committed virtual-memory regions via
IDebugDataSpaces2::QueryVirtual (the DbgEng wrapper over VirtualQueryEx),
walking the address space from 0 and advancing by each region's size until
QueryVirtual reports the end.

Only MEM_COMMIT regions that are neither guard nor no-access pages are
reported. Permissions are derived from the page Protect flags; MEM_MAPPED
regions are marked shared; and image-backed (MEM_IMAGE) regions get their
backing module's image path as the name via GetModuleByOffset/
GetModuleNames.

The DbgEng TTD and kernel adapters inherit this via DbgEngAdapter. The
non-DbgEng WindowsNativeAdapter still uses the default empty map for now.

Note: this adapter only builds on Windows, so it is validated by CI rather
than the local (macOS) build.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Enumerate the target's committed virtual-memory regions with VirtualQueryEx
on the process handle, walking the address space from 0 and advancing by
each region's size until the query reports the end.

Mirrors the DbgEng implementation: only MEM_COMMIT regions that are neither
guard nor no-access pages are reported; permissions come from the page
Protect flags; MEM_MAPPED regions are marked shared; and image/file-backed
regions get their backing file path via the existing GetModuleNameFromHandle
helper (the "<unknown>" sentinel is mapped to an empty name for anonymous
mappings).

With this, all Windows adapters (DbgEng + TTD + kernel via inheritance, and
WindowsNative) report a memory map.

Note: this adapter only builds on Windows, so it is validated by CI rather
than the local (macOS) build.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

GdbMiAdapter derives directly from DebugAdapter (not GdbAdapter), so it did
not inherit the RSP adapter's memory map and was returning the empty
default. Implement it by parsing "info proc mappings" -- the same command it
already uses for GetModuleList -- but keeping every region and reading the
permissions.

The Perms column is present on GDB 8.0+ and its position can vary, so it is
detected by pattern rather than fixed index; on older GDB that omits it, the
region is still reported as readable. The trailing objfile/pseudo-name (e.g.
[stack]) is used as the region name.

Builds locally (this adapter is compiled on macOS).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Add "Select In Binary View" context action: navigates to the region's
  start and selects its full [start, end) range in the current view.
- Add "Save Region To Disk..." context action: reads the region via
  ReadMemory and writes it to a user-chosen file, warning on partial
  reads and erroring when nothing is readable.
- Fix Copy so that a multi-cell selection copies every selected cell
  (grouped by row, tab-separated columns, newline-separated rows, in
  visual order) instead of only the first cell.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>